TrustRadius Insights
TeamCity has proven to be an invaluable tool for software development teams across various organizations. Users have utilized TeamCity in …
Overview
What is TeamCity?
TeamCity is a continuous integration server from Czeck company JetBrains.
Recent Reviews
Reviewer Pros & Cons
Pricing
N/A
Unavailable
What is TeamCity?
TeamCity is a continuous integration server from Czeck company JetBrains.
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://www.jetbrains.com/teamcity/buy
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
Alternatives Pricing
What is Codemagic?
Codemagic is a developer's CI/CD tool for mobile app projects. Build Android, iOS, React Native, Ionic, Unity, and Flutter projects on Codemagic.Codemagic uses its own CLI tools under the hood to perform complicated tasks like code signing and distribution to the stores. These are open-sourced and…
What is Appsmith?
Appsmith is an open source framework to build admin panels, CRUD apps and workflows.
Product Demos
Sitecore CI/CD with TeamCity and TDS Demo
YouTube
Redgate DLM Demo (with TFS, TeamCity, & Octopus Deploy)
YouTube
CI/CD with JetBrains TeamCity | TeamCity Tutorial
YouTube
Demo Teamcity Build Project 2 (end)
YouTube
TeamCity Fundamental Tutorial for Beginners with Demo || Class - 01 || By Visualpath
YouTube
TeamCity demo - part 1
YouTube
Product Details
- About
- Competitors
- Tech Details
- FAQs
What is TeamCity?
A Continuous Integration and Deployment server that provides out-of-the-box test intelligence, real-time reporting on build problems, and boasts scalability. It is available both as an on-premises and a cloud-based version.
TeamCity Video
Getting Started with TeamCity
TeamCity Competitors
TeamCity Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Frequently Asked Questions
TeamCity is a continuous integration server from Czeck company JetBrains.
The most common users of TeamCity are from Mid-sized Companies (51-1,000 employees).
Comparisons
Compare with
Reviews and Ratings
(58)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Pros
- Cons
- Recommendations
TeamCity has proven to be an invaluable tool for software development teams across various organizations. Users have utilized TeamCity in their agile project management systems, specifically within the web development team, to streamline their workflow and enhance productivity. By seamlessly integrating their git repositories with their ticketing systems, users have been able to test and release code from the development environment to the production environment with ease.
The software's automation testing capabilities have been critical for both development and product support. With TeamCity, users have been able to evaluate and integrate numerous projects, pulling together over 300 components of their SaaS-based product. This has allowed them to schedule, execute, and generate reports for various types of automation testing, ensuring the quality and reliability of their software.
One of the standout features of TeamCity is its user-friendly interface. Users have praised how easy it is to navigate and manage builds and releases within the system. Additionally, TeamCity offers flexible templates through its templates, variables, and parameterization capabilities. This enables users to create common solutions, such as deploying MVC applications to IIS, quickly and efficiently.
TeamCity seamlessly integrates with several popular platforms like Git, Azure, AWS, and Visual Studio Team Services. This integration allows development teams to leverage existing tools in their CI/CD build process without any hassle.
While users appreciate the functionality provided by TeamCity, some have expressed a desire for more comprehensive deployment visualization features. However, this minor limitation does not detract from the overall effectiveness of the software.
Overall, TeamCity has become an essential tool for development teams looking to implement continuous integration and continuous deployment practices. By providing immediate feedback on code issues and enabling thorough testing before delivery to customers, TeamCity ensures a smooth and efficient development process. Its ease of configuration and implementation also makes it suitable for small organizations with multiple projects. With its ability to meet quality expectations by running automated unit tests and handling various environments, customers find great value in using TeamCity for their software development needs.
Reliable Performance: Many users have praised the product for its reliable performance. Several reviewers have stated that the product consistently meets their expectations and performs well without any issues.
User-friendly Interface: A significant number of customers have appreciated the user-friendly interface of the product. Numerous users mentioned that the interface is intuitive and easy to navigate, making it simple for them to use and understand all its features.
Great Customer Support: Several reviewers have expressed their satisfaction with the excellent customer support provided by the company. Users have reported positive experiences while seeking assistance from customer support representatives who were helpful, knowledgeable, and prompt in resolving their queries or concerns.
Long and Manual Upgrade Process: Many users have expressed frustration with the lengthy and manual upgrade process for TeamCity. They have found it to be time-consuming and cumbersome, requiring significant effort.
Lack of SaaS-based Solution: Several reviewers have mentioned their disappointment in the lack of a SaaS-based solution for TeamCity. This means that users are required to host and maintain a large server along with multiple build agents, which can be inconvenient and resource-intensive.
Weak Pipeline Visualization: A common concern among users is the weakness of TeamCity's pipeline visualization feature. They feel that it could benefit from improvements in terms of clarity and usability, as it currently falls short compared to other aspects of the platform.
- Users recommend TeamCity over Jenkins for its additional features, ease of use, and integration capabilities.
- They highly recommend TeamCity to IT companies and suggest that it is worth the investment for enterprise continuous integration.
- Users also recommend self-hosting TeamCity for small companies and mention its value compared to other services.
- Furthermore, they recommend taking advantage of the free trial, checking available plugins, and evaluating new major versions and security risks.
- Overall, users think TeamCity is a great product for build automation and continuous integration and consider it as one of the best CI tools available.
Attribute Ratings
Reviews
(1-3 of 3)Companies can't remove reviews or game the system. Here's why
TeamCity is being used across my company. We have integrated TeamCity with the CI/CD pipeline. This is solving number of problems which occur if we do not have CI/CD in place. Configuring node servers to build the projects is easy. We can easily configure the properties while building the specific branch. Can easily build multiple feature/develop/release branches at once. It gives all build related information at one place, so can troubleshoot problem in build easily. Basic implementation of application is easy.
- Selection of build server for specific build
- We can add configurable properties
- One stop solution to create deployable package
- Initial and basic setup is easy
- It is not plug and play thing
- Need more specific configurations for smaller projects as well
- Online help is less available
- Basic implementation is easy but I think feature add on can be complex as it involve some language knowledge as well.
- Integrate with Sonar to highlight potential bugs
- can be configured on big scale
- We can add project specific settings/configurations.
- Track all builds from your microservices architecture at one place.
- It is always better to have code quality check tolls integrated in CI/CD
- For small projects also we have to go through same long path
- This application is suitable for big microservices architecture, where we have many services
This application is easy to install and deploy at site than most of the similar solutions in market. Easy user interface is one of the reason it can be installed. However each software have its good points and bad points. Study your organizations case and then only choose between applications.
We used TeamCity as our Core Continuous Integration solution for four years. I love TeamCity's easy to use interface, and the way builds and releases are linked together in dependency Chains. I found it particularly helpful that Builds can be run separately, or in advance of Releases - and then when Releases are run the Builds only run again if the code has changed. TeamCity's Templates, Variables, and Parameterization capabilities also made it very easy to establish a flexible template for common solutions such as deploying MVC applications to IIS. Once templates were configured I could create a "build and release" for a new project in less than 10 minutes.
While TeamCity has a simple to use and understand chaining mechanism, allowing builds to call "builds and releases" to rely on multiple dependency chains - TeamCity's PipeLine visualization capabilities are one of its weakest points. I had a complex build across five different environments consisting of eight different solutions and over 20 deployment targets. During a major update, it would have been nice to visualize the deployment pipeline and "watch" the deployment process for issues - but that really isn't possible with TeamCity. Outside of that, TeamCity worked great, integrated well with all of our platforms: Git, Azure, AWS, Visual Studio Team Services.
Great Product.
While TeamCity has a simple to use and understand chaining mechanism, allowing builds to call "builds and releases" to rely on multiple dependency chains - TeamCity's PipeLine visualization capabilities are one of its weakest points. I had a complex build across five different environments consisting of eight different solutions and over 20 deployment targets. During a major update, it would have been nice to visualize the deployment pipeline and "watch" the deployment process for issues - but that really isn't possible with TeamCity. Outside of that, TeamCity worked great, integrated well with all of our platforms: Git, Azure, AWS, Visual Studio Team Services.
Great Product.
- Build: Parameterization, Chaining from multiple sources, Templates, and general ease of use.
- Release: Works extremely well with "Build" process.
- Updates and Upgrades are simple, effective, and reliable.
- Pipeline Visualization: TeamCity's weakest area
- TeamCity was a key contributor to our organization's adoption of Agile.
- TeamCity made it possible to KILL "It works on my laptop" conversations with Developers. If it does not compile in TeamCity - the project is not deployable. TeamCity's easy to use interface made it possible to quickly adopt a "Deploy Only from TeamCity" policy, further ensuring TeamCity Builds were the gold-standard for well-configured source code.
TeamCity is a great on-premise Continuous Integration tool.
Visual Studio Team Services (VSTS) is a hosted SAAS application in Microsoft's Cloud.
VSTS is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and Release System only.
TeamCity's interface is easier to use than VSTS, and neither have a great deployment pipeline solution. But VSTS's natural integration with Microsoft products, Microsoft's Cloud, Integration with Azure Active Directory, and free, private, Source Code repository - offer additional features and capabilities not available with Team City alone.
Visual Studio Team Services (VSTS) is a hosted SAAS application in Microsoft's Cloud.
VSTS is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and Release System only.
TeamCity's interface is easier to use than VSTS, and neither have a great deployment pipeline solution. But VSTS's natural integration with Microsoft products, Microsoft's Cloud, Integration with Azure Active Directory, and free, private, Source Code repository - offer additional features and capabilities not available with Team City alone.
TC is used across our organization to do builds for all our apps and services. We started using it to replace our custom build and deploy system because we needed something more flexible and customizable, and something that did not need a fully dedicated support team.
- Fully customizable build process. Each step of the build process can be parameterized and customized to address specific needs of particular applications. This allowed us to easily convert from a custom VM-based environment to our current Docker-based environment.
- Manages large numbers of build agents seamlessly. This allows us to run multiple builds on many different applications in a most efficient manner.
- Build steps can be managed in an arbitrary manner, allowing some parts of the process to proceed in parallel while restricting others to depend on completion of all relevant steps.
- The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations.
- Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious.
- When we initially started using it, there was a big impact because it made our build/deploy more reliable and flexible, as well as quicker.
- Over time, we found that it was relatively easy to change our build and deployment system to our current Docker-based system. This has not only allowed us to continue improving our time to deploy but also to distribute the build process to engineers rather than have everything controlled by a dev infrastructure team.
- Our most recent change has been to diversify our data centers to support international data centers. TC has made this process more or less seamless, although we no longer use it specifically for the deployment stage for various reasons.